System, apparatus, and method for modifying captured data packets

ABSTRACT

Systems, apparatus, and methods for modifying a captured data packet included in a traffic flow of captured data packets are described. A captured data packet may be analyzed in order to, for example, locate a predefined segment of data included in the received captured data packet, determine a type of data included in the data packet, and determine content included in the data packet. The data packet may then be modified based upon the analysis. Exemplary modifications include deleting a portion of the data included in the data packet, truncating the data packet, and modifying data included in the predefined segment.

RELATED APPLICATION

This application is a NONPROVISIONAL of, claims priority to, andincorporates by reference U.S. Provisional Patent Application61/266,091, filed 2 Dec. 2009.

FIELD OF THE INVENTION

The present invention relates to systems, apparatus, and methodsmodifying a captured data packet included in a traffic flow of captureddata packets.

BACKGROUND

In conventional communication networks, a traffic flow of data packetstransmitted through the communication network may be captured andforwarded to a network tap device. The network tap device then forwardsthe full traffic flow of captured network traffic, as received, to anexternal monitoring device. This transmission of the full traffic flowof captured network traffic to external monitoring devices has manydrawbacks.

For example, many external monitoring devices are specialized such thatthey analyze and/or monitor only specific segments of a captured datapacket or types of captured traffic. Thus, these specialized externalmonitoring devices need to receive only relevant captured data packetsegments or types of captured traffic. Receipt of the full traffic flowof captured network traffic serves to require the specialized externalmonitoring devices to filter out irrelevant information from the fulltraffic flow of captured network traffic prior to executing it'sanalysis and or monitoring functions. This filtering causes results inan increased burden on the resources, such as bandwidth and processingtime, on both the communication network and the network tap.

Another drawback to transmission of unmodified captured traffic flowsresults when inappropriate information is transmitted to an externalmonitoring device. For example, when the external device is atelecommunications monitor attempting to monitor the quality-of-servicefor a telecommunicated conversation between two individuals, receipt ofthe all data included in the conversation may be an unnecessary use ofbandwidth and, in a case where receipt of all data included in theconversation is of a violation of wire-tapping laws, illegal.

A further drawback to the transmission of unmodified captured trafficoccurs because the external monitoring devices are not aware of anoriginating port for captured network traffic or when, eithersequentially or chronologically, captured network traffic enters intothe communication network and/or network tap.

SUMMARY

Systems, apparatus, and methods for modifying a captured data packetincluded in a traffic flow of captured data packets are hereindisclosed. The traffic flow of captured data packets may be received bya network captured traffic distribution device via, for example, amirror port resident on a source of the captured datisa packets and/or atraffic capture point located along a communication link between twocommunicating devices.

A data packet included in the traffic flow of captured data packets maybe analyzed in order to locate a predefined segment of data included inthe received data packet. Exemplary predefined segments include avirtual local area network (VLAN) tag, Gateway General Packet RadioService (GPRS) Tunneling Protocol (GTP) information, multi-protocollabel switching (MPLS) information, data characterized as “private” by aprivacy policy, data characterized as “sensitive” under a contract, datacategorized as “classified” by a governmental organization, and datacategorized as a “trade secret” by a business organization.

In one embodiment, analysis of the data packet may include counting aspecified number of bytes into the data packet. In another embodiment,analysis of the data packet may include analyzing the data packetaccording to a privacy policy, a communication protocol, a term includedin a contract, and/or a law, such as a wire-tapping law.

The predefined segment of data may then be modified. Exemplarymodifications of the predefined segment include deleting data from thepredefined segment, adding data to the predefined segment, and changingdata included in the predefined segment. In one instance, the modifiedpredefined segment may have an even number of bytes. In anotherinstance, modification of the predefined segment may bring transmissionof the data packet to an external device into compliance with, forexample, a contract, privacy policy, communication protocol, and/or law.

An egress port assigned to the data packet may then be determined. Thisdetermination may be based on, for example, configuration informationstored at the network captured traffic distribution device. On someoccasions, the egress port may be a monitor port. In one embodiment, thedetermination of the egress port assigned to the data packet including amodified predefined segment may be based on configuration informationstored on the network captured traffic distribution device. Then, thedata packet, including the new data segment, may be transmitted to theassigned egress port.

In one embodiment, modification of the data packet includes truncatingthe data packet. In this embodiment, the data packet may be analyzed inorder to locate a predefined segment of data included in the receiveddata packet. Analysis of the data packet may include counting aspecified number of bytes into the data packet.

The data packet may be truncated to include only the predefined segmentof data. In one embodiment, truncating the data packet may bringtransmission of the data packet to an external device into compliancewith, for example, a contract, privacy policy, communication protocol,and/or law. On occasions when the data packet includes a payloadsegment, the data packet may be truncated to remove a portion of thepayload segment from the data packet.

An egress port assigned to the data packet may then be determined. Thisdetermination may be based on, for example, configuration informationstored at the network captured traffic distribution device. On someoccasions, the egress port may be a monitor port. In one embodiment, thedetermination of the egress port assigned to the truncated data packetmay be based on configuration information stored on the network capturedtraffic distribution device. Then, the truncated data packet may betransmitted to the assigned egress port.

Systems, apparatus, and methods for deleting a predefined segment from acaptured data packet included in a traffic flow of captured data packetsare also herein disclosed. The traffic flow of captured data packets maybe received by a network captured traffic distribution device via, forexample, a mirror port resident on a source of the captured data packetsand/or a traffic capture point located along a communication linkbetween two communicating devices.

A data packet included in the traffic flow of captured data packets maybe analyzed in order to locate a predefined segment of data included inthe received data packet. Analysis of the data packet may includecounting a specified number of bytes into the data packet. Thepredefined segment of data may then be modified. This analysis mayinclude, for example, analyzing the data packet according to at leastone of a privacy policy, a communication protocol, a term included in acontract, and a law. Exemplary predefined segments include a VLAN tag,GTP information, MPLS information, data characterized as “private” by aprivacy policy, data characterized as “sensitive” under a contract, datacategorized as “classified” by a governmental organization, and datacategorized as a “trade secret” by a business organization.

Once located, the predefined segment of data may be deleted from thedata packet. In one embodiment, deleting the predefined segment of datafrom the data packet may bring transmission of the data packet to anexternal device into compliance with, for example, a contract, privacypolicy, communication protocol, and/or law.

Then, an egress port assigned to the data packet may then be determined.This determination may be based on, for example, configurationinformation stored at the network captured traffic distribution device.On some occasions, the egress port may be a monitor port. In oneembodiment, the determination of the egress port assigned to the datapacket including a deleted predefined segment may be based onconfiguration information stored on the network captured trafficdistribution device. Then, the data packet, without the deletedpredefined segment, may be transmitted to the assigned egress port.

Exemplary network captured traffic distribution devices disclosed hereinmay include a plurality of ingress ports, a memory, a plurality ofingress ports for receiving a traffic flow of captured data packets, aplurality of egress ports and application specific integrated circuit(ASIC), a processor, and/or a field programmable gate array (FPGA). Theingress ports may be configured to receive a traffic flow of captureddata packets from a source.

The memory may be configured to store instructions executable by atleast one of the ASIC, processor, and FPGA. Execution of theinstructions may enable the modification of a data packet, removal of atarget segment from a data packet, truncation of a data packet,insertion of a new data segment into a data packet, modification of atarget segment of a data packet, determining an egress port of aplurality of egress ports assigned to the data packet, and transmittinga data packet to the assigned egress port. The ASIC, processor, and/orFPGA may be configured to execute one or more of the instructions storedin the memory. The plurality of egress ports may be configured totransmit a data packet externally from the network captured trafficdistribution device.

BRIEF DESCRIPTION OF THE FIGURES

The present invention is illustrated by way of example, and notlimitation, in the figures of the accompanying drawings in which:

FIG. 1 is a block diagram depicting a network communication system inaccordance with an embodiment of a present invention;

FIG. 2 is a block diagram depicting a network captured trafficdistribution device, in accordance with an embodiment of the presentinvention;

FIG. 3A is a block diagram depicting a data packet, in accordance withan embodiment of the present invention;

FIG. 3B is a block diagram of a data packet including a port stamp, inaccordance with an embodiment of the present invention;

FIG. 3C is a block diagram of a data packet including a time stamp, inaccordance with an embodiment of the present invention;

FIG. 3D is a block diagram depicting a data packet including a timestamp and a port stamp, in accordance with an embodiment of the presentapplication;

FIG. 3E is a block diagram depicting a data packet including apredefined segment, in accordance with an embodiment of the presentapplication;

FIG. 3F is a block diagram depicting a data packet with a deletedpredefined segment, in accordance with an embodiment of the presentapplication;

FIG. 3G is a block diagram of a truncated data packet, in accordancewith an embodiment of the present application;

FIG. 3H is a block diagram of a data packet including a new datasegment, and in accordance with an embodiment of the presentapplication;

FIG. 3I is a block diagram of a data packet including a modifiedpredefined segment, in accordance with an embodiment of the presentinvention;

FIG. 4 is a flow chart depicting a process for inserting a port stampinto a data packet, in accordance with an embodiment of the presentinvention;

FIG. 5 is a flow chart depicting a process for inserting a time stampinto a data packet, in accordance with an embodiment of the presentapplication;

FIG. 6 is a flow chart depicting a process for inserting a time stampand a port stamp into a data packet, in accordance with an embodiment ofthe present application;

FIG. 7 is a flow chart depicting a process for deleting a predefinedsegment from a data packet, in accordance with an embodiment of thepresent invention;

FIG. 8 is a flow chart depicting a process for truncating a data packet,in accordance with an embodiment of the present invention;

FIG. 9 is a flow chart depicting a process for inserting a new datasegment into a data packet, in accordance with an embodiment of thepresent invention; and

FIG. 10 is a flow chart depicting a process for modifying a data segmentincluded in a data packet, in accordance with an embodiment of thepresent invention.

WRITTEN DESCRIPTION

At times, it may be desirable to analyze and/or modify captured datapackets received by a network captured traffic distribution device inorder to, for example, facilitate various functions performed eitherinternally to, or externally from, the network captured trafficdistribution device.

FIG. 1 is block diagram depicting a network communication system 100capable of executing any of the methods herein described. System 100 maybe, for example, a telecommunication system such as a Global System forMobile communication (GSM) system or a multi-protocol label switching(MPLS) system. In some embodiments, system 100 may be Gateway GeneralPacket Radio Service (GPRS) system, an Enhanced Data Rates for GSMEvolution (EDGE) system, an Enhanced GPRS (EGPRS) system, anInternational Mobile Telecommunications-2000 (IMT-2000) system, an IMTSingle Carrier (IMT-SC) system, an Universal Mobile TelecommunicationsSystem (UMTS) system, a Long Term Evolution (LTE) system, a CodeDivision Multiple Access (CDMA) system, a system compliant with the IEEE802.1 Q standard for configuring virtual LANs (VLAN), or a systemenabled to transmit and/or receive data packets including VLAN tags.

System 100 may include a communication device 110. Exemplarycommunication devices 100 include personal computers, mobile computingdevices, and mobile telephones. Communication device 110 may generate adata packet 140 and transmit data packet 140 to a routing device, suchas routing device 120 via a communication link. Routing device 120 maybe any router enabled to route data packets through communication system100.

System 100 may also include a network captured traffic distributiondevice 130 which may be any network captured traffic distribution devicecapable of receiving captured network traffic. Network captured trafficdistribution device 130 may include a plurality of ingress and egressports. In some cases, an egress port may be a monitor port. Networkcaptured traffic distribution device 130 may also be communicativelycoupled so as to provide information to and/or receive instructions froma user and/or administrator 155. User/administrator 155 may be, forexample, a user and/or administrator of, for example, system 100 and/ornetwork captured traffic distribution device 130. User/administrator 155may communicate, for example, configuration information and/orinstructions to network captured traffic distribution device 130.

Network captured traffic distribution device 130 may be communicativelycoupled to a mirror port 160 present on routing device 120 via aningress port and may receive a traffic flow of captured data packets,including data packet 140, from routing device 120 via mirror port 160.Network captured traffic distribution device 130 may also becommunicatively coupled to a traffic capture point 165 located along acommunication link between communication device 110 and routing device120 and thereby may capture data packets, like data packets 140, via aninline network traffic capture at traffic capture point 165.

Network captured traffic distribution device 130 may be enabled toperform various manipulations and/or modifications of data packet 140thereby producing a data packet 145. Further details regarding themanipulation and/or modification of data packets are provided below withreference to FIGS. 3A-10. Network captured traffic distribution device130 may communicate modified data packet 145 to an external device 150via, for example, an egress port. Exemplary external devices 150 includenetwork monitors and network analyzing devices.

System 100 may also include a Global Positioning System (GPS) receiver170. GPS receiver 170 may receive a GPS signal from one or more sourcesand may transmit this signal to network captured traffic distributiondevice 130. Network captured traffic distribution device 130 mayincorporate a time value derived from the GPS signal into a time stampinserted into a data packet, like data packet 140, in order to generatedata packet 145.

FIG. 2 is a block diagram depicting network captured trafficdistribution device 130 capable of executing any of the methods hereindescribed. Network captured traffic distribution device 130 includes aplurality of ingress ports 210 and a plurality of egress ports 220. Oneor more ingress ports 210 and/or egress ports to 220 may be configuredto operate in duplex and/or half-duplex mode. One or more egress ports220 may be configured as a monitoring and/or stacking port. Data packetssuch as data packet 140 may be received by network captured trafficdistribution device 130 via one or more ingress port 210. Data packetsmay be received from, for example, a mirror port, like mirror port 160,and/or an inline traffic capture point, like inline traffic capturepoint 165.

Received data packets may be forwarded from an ingress port 210 to anapplication specific integrated circuit (ASIC) 235 communicativelycoupled to ingress port 210. ASIC 235 may perform a switching functionand may forward a received data packet to a processor 215, and egressport 220, and/or an ingress port 210. ASIC 235 may also manipulate areceived data packet according to one or more instructions stored in,for example, memory 225.

Processor 215 may be coupled to ASIC 235, a memory 225, and/or amanagement port 230. Processor 215 may be any appropriate processing orcentral processing unit (CPU) device. Processor 215 may process orreceive data packets according to one or more instructions resident inmemory 225. Processor 215 may be enabled to manipulate the data includedin a data packet, such as data packet 140. Exemplary manipulationsinclude inserting a port stamp into a data packet, inserting a timestamp into a data packet, removing a predefined segment from a datapacket, truncating a data packet, inserting new data into a data packet,and/or modifying a predefined segment of the data packet. Processor 215may also calculate a new frame check sequence (FCS) and/or a cyclicredundancy check (CRC) to be incorporated into a data packet, like datapacket 145. Processor 215 may be managed by, for example, a user and/oradministrator, like user/administrator 155 via, for example, amanagement port, like management port 230.

Memory 225 may be any appropriate data storage device, like staticrandom access memory (SRAM), dynamic random access memory (DRAM),read-only memory (ROM), flash memory, a magnetic computer storage device(e.g. hard disk, floppy disk, and magnetic tape), and optical media andmay store one or more instructions executable by processor 215 and/orASIC 235.

System 100 may include a field programmable gate array (FPGA) 240coupled to ASIC 235. FPGA 240 may include a first counter 245 and asecond counter 250. FPGA 240 may be enabled to manipulate the dataincluded in a data packet, such as data packet 140. Exemplarymanipulations include inserting a port stamp into a data packet,inserting a time stamp into a data packet, removing a predefined segmentfrom a data packet, truncating a data packet, inserting new data into adata packet, and/or modifying a predefined segment of the data packet.FPGA 240 may also calculate a new frame check sequence (FCS) and/or acyclic redundancy check (CRC) to be incorporated into a data packet,like data packet 145.

In one embodiment, two counters, such as first counter 245 and secondcounter 250, may be resident in and/or maintained by a network capturedtraffic distribution device like network captured traffic distributiondevice 130, or a FPGA, like FPGA 240. First counter 245 and/or secondcounter 250 may each maintain a value of, for example, 32 bits inlength. First counter 245 may, for example, maintain a value equal tothe number of seconds that have passed since an arbitrarily chosen date,like Jan. 1, 1980. First counter 245 may be adapted such that it may beinitialized to a value of zero after a reset operation is performed andmay be further adapted to be loaded with an initial value and/or asystem time by an external device from, for example, a processor likeprocessor 215. These adaptations may allow the processor to load asystem time into first counter 245.

A system time may be maintained by, for example, processor 215 or adevice external to the processor. In some embodiments, a time valueloaded onto first counter 245 may be sourced from and/or calibrated byan external timer or timing source like GPS receiver 170. A time valuemay also be received from a port timer associated with, for example, aningress port via which a data packet is received.

Second counter 250 may, for example, count an interval representing afraction of a currently elapsing time interval, and may be representedas a decimal integer. In some cases, the time interval may be amillisecond, a microsecond, or a nanosecond. The second counter mayreset when a complete time interval has elapsed (i.e., a decimal valueof 1,000 or greater for milliseconds, 1,000,000 or greater formicroseconds or 1,000,000,000 or greater for nanoseconds) and firstcounter 245 may be incremented by, for example, a value of 1.

Second counter 250 may be incremented according to a frequency ofincrimination of a clock, maintained by, for example, a processor, asystem clock, or a GPS receiver. A frequency of incrimination of a clockmay also be referred to as a clock cycle and an incrimination of a clockmay be referred to as a tick. A clock cycle may or may not directlycorrespond to an interval of time and may vary from clock to clock. Thenumber of increments added to second counter 250 per tick may varydepending on, for example, a clock cycle of a clock transmitting asignal to second counter 250. In this case, receipt, by second counter250, of a signal from a clock indicating a tick may result in atriggering of an adder to add a number of increments representative ofthe tick to second counter 250, rather than simply incrementing thecount value of second counter 250 by 1. For example, a 50 MHz clockadvances one increment every 20 ns, thus the clock cycle of the 50 MHzclock is 20 ns and each tick of the 50 MHz clock represents 20 ns. Thus,each tick of the 50 MHz clock may cause an addition of 20 ns to secondcounter 250.

A clock transmitting ticks to first counter 245 and/or second counter250 may be subject to various inaccuracies that may, in turn, affect theaccuracy of the interval in which ticks are transmitted. For example,some system clocks suffer from inaccuracies on the order of +/−500 nswithin a single second while the accuracy of other types of clocks, suchas crystal oscillators gradually becomes more inaccurate over time.Various time increment validation procedures may be performed in orderto correct for such inaccuracies. For example, a running sample of ticksmay be analyzed to determine whether there are any inaccuracies in theinterval at which ticks are delivered. From this analysis, an offset maybe determined such that, an offset value is used to adjust anincremental adder of second counter 250 every n clock cycles. Theincremental adder may be resident in, for example, second counter 250 oran FPGA, like FPGA 240. Thus, the adder may increment by, for example,19 ns every n clock cycles to slow down a clock, or by, for example, 21ns every n clock cycles to speed up a clock.

FIG. 3A is a block diagram illustrating an exemplary data packet 301.Data packet 301 includes a header 315, a payload 320, and a FCS/CRC 322and may resemble data packet 140. Exemplary header 315 may include, forexample, address information and other information, as needed, for thetransmission of data packet 301 through a network communication system,like network communication system 100. Payload 320 may include anypayload or data appropriate for data packet 301. FCS/CRC 322 may includeframe check sequence (FCS) and/or cyclic redundancy check (CRC)information necessary for compliance with one or more system protocols,communication protocols, and/or the routing of the packet through anetwork communication system, like network communication system 100.

FIG. 3B is a block diagram illustrating an exemplary modified datapacket 302 including header 315, payload 320, a port stamp 330, and anew FCS/CRC 325. In some cases, modified data packet 302 may be amodified form of data packet 301 and/or 140 and may resemble data packet145. Modified data packet 302 may be generated via a process forinserting a port stamp into a data packet, like process 400, which isdiscussed below with reference to FIG. 4. Port stamp 330 may be asegment of data that indicates an ingress port identity associated witha data packet received by, for example, a network captured trafficdistribution device, like network captured traffic distribution device130. Although FIG. 3B indicates that port stamp 330 is insertedimmediately prior to new FCS/CRC 325, port stamp 330 may be insertedinto any location within modified data packet 302.

FIG. 3C is a block diagram illustrating a modified data packet 303including header 315, payload 320, a time stamp 335, and new FCS/CRC325. Modified data packet 303 may be a modified form of data packet 301and/or 140 and may resemble data packet 145. In some cases, modifieddata packet 303 may be generated via a process for inserting a timestamp into a data packet, like process 500, which is discussed belowwith reference to FIG. 5. Time stamp 315 may be a segment of data thatindicates an arrival time of a data packet at a network captured trafficdistribution device, like network captured traffic distribution device130. New FCS/CRC 325 may include a frame check sequence and/or cyclicredundancy check that is modified to incorporate the informationinserted into modified data packet 303. Although FIG. 3C indicates thattime stamp 335 is inserted immediately prior to new FCS/CRC 325, timestamp 335 may be inserted into any location within modified data packet303.

FIG. 3D is a block diagram illustrating an exemplary modified datapacket 304 including header 315, payload 320, time stamp 335, port stamp330, and new FCS/CRC 325. In some cases, modified data packet 304 may bea modified form of data packets 140, 301, 302, and/or 303 and mayresemble data packet 145. New FCS/CRC 325 may be modified to indicatethe port stamp and time stamp that has been added to data packet 304.Although FIG. 3D indicates that port stamp 330 is inserted immediatelyprior to new FCS/CRC 325, and time stamp 335 is inserted immediatelyprior to port stamp 330, port stamp 330 and time stamp 335 may beinserted into any location within modified data packet 304. In somecases, modified data packet 304 may be generated via a process forinserting a time stamp and/or a port stamp into a data packet, likeprocess 600, which is discussed below with reference to FIG. 6.

FIG. 3E is a block diagram illustrating a data packet 305 includingheader 315, predefined segment 340, a payload 320 and FCS/CRC 322. Datapacket 305 may resemble data packet 301 and/or data packet 140.Predefined segment 340 may include any segment of data packets that maybe of interest to, for example, a user and/or administrator, likeuser/administrator 155, of a network captured traffic distributiondevice, like network captured traffic distribution device 130, and/or asystem like system 100. Predefined segment 340 may be of any length,including for example, the entire payload 320, header 315, FCS/CRC 322and/or any portion thereof. Predefined segment may be located at anyposition within data packet 305, including, for example, header 315,payload 320, and/or FCS/CRC 322. Exemplary content included in apredefined segments include multi-protocol label switching (MPLS)information, VLAN tags, GPRS tunneling protocol (GTP) information for aGTP header, corrupted data, address information, and/or data type.Although FIG. 3E indicates that predefined segment 340 is locatedimmediately after header 315, predefined segment 340 may be located atany position within data packet 305.

FIG. 3F is a block diagram illustrating a modified data packet 306including header 315, payload 320, and new FCS/CRC 325 whereinpredefined segment 340 has been deleted. Modified data packet 306 may bea modified form of data packet 301 and/or 305 and may resemble modifieddata packet 145. New FCS/CRC 325 may indicate contents of modified datapacket 306 without predefined segment 340. In some cases, modified datapacket 306 may be generated via a process for modifying a predefinedsegment included in a data packet, like process 700, which is discussedbelow with reference to FIG. 7.

FIG. 3G is a block diagram illustrating a truncated data packet 307including header 315, predefined segment 340, and new FCS/CRC 325.Truncated data packet 308 may be a modified form of data packet 140,301, 305, and/or 306 and may resemble data packet 145. As shown, datapacket 307 has been truncated to remove payload 320. However, datapacket 307 may be truncated to include any amount of data. For example,a truncated data packet 307 can include only header 315, only newFCS/CRC 325, only a portion of payload 320, and/or a portion thereof.New FCS/CRC 325 may indicate the truncated form of data packet 307. Insome cases, modified data packet 307 may be generated via a process fortruncating a data packet, like process 800, which is discussed belowwith reference to FIG. 8.

FIG. 3H is a block diagram illustrating an exemplary modified datapacket 308 that includes header 315, new data segment 345, payload 320and new FCS/CRC 325. Modified data packet 309 may be a modified form ofdata packet 140, 301, and/or 305 and may resemble data packet 145. Newdata segment 345 may include, for example, any data a user and/oradministrator, like user/administrator 155, of a network capturedtraffic distribution device, like network captured traffic distributiondevice 130, and/or a system like system 100 may desire to insert into adata packet like data packet 140, 301, and/or 305. For example, new datasegment 345 may include address information, a time of arrival, aningress port identity, an egress port identity, and a VLAN tag. AlthoughFIG. 3H indicates that new data segment 345 is inserted immediatelyafter header 315, new data segment 345 may be inserted into any locationwithin modified data packet 308. In some cases, modified data packet 308may be generated via a process for inserting a new data segment into adata packet, like process 900, which is discussed below with referenceto FIG. 9.

FIG. 3I is a block diagram illustrating a modified data packet 309including header 315, modified predefined segment 350, payload 320 andnew FCS/CRC 325. Modified data segment 350 may be a modified form ofdata packet 140, 301, and/or 305 and may resemble modified data packet145. Modified predefined segment 350 may be a modified form of, forexample, predefined segment 340 and may be modified according to, forexample, a desire of a user and/or administrator, likeuser/administrator 155, of a network captured traffic distributiondevice, like network captured traffic distribution device 130, and/or asystem like system 100. Although FIG. 3H indicates that modifiedpredefined segment 350 is inserted immediately after header 315,modified predefined segment 350 may be inserted into any location withinmodified data packet 308. In some cases, modified data packet 309 may begenerated via a process for modifying a data segment of a data packet,like process 1000, which is discussed below with reference to FIG. 10.

FIG. 4 is a flow chart illustrating a process 400 for inserting a portstamp, like port stamp 330, into a data packet such as data packet 140,301, and/or 305. Process 400 may be performed by, for example, a networkcommunication system like network communication system 100, a networkcaptured traffic distribution device like network captured trafficdistribution device 130, and/or an FPGA like FPGA 240. A data packetgenerated and/or modified by an execution of process 400 may resemble,for example, data packet 145 and/or 302.

In step 405, a traffic flow of captured data packets may be received by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.The traffic flow of data packets may be received via, for example, amirror port like mirror port 160 and/or a traffic capture point locatedalong a communication link between two communicating devices liketraffic capture point 165. The traffic flow of data packets may bereceived at a rate of, for example, ten Mega bites per second, onehundred Mega bites per second, one Gigabit per second, ten Gigabits persecond, 40 Gigabits per second, 40 Gigabits per second via densewavelength-division multiplexing, and 100 Gigabits per second.

In step 410, it may be determined whether a data packet is received viaan inline capture point or a mirror port. When a data packet is receivedvia an inline capture point the data packet may be echoed to an inlinepair-port resident on, for example, a network captured trafficdistribution device like network captured traffic distribution device130 (step 415). In some embodiments, an inline pair-port may be anegress port resident in, for example, the network captured trafficdistribution device.

When the data packets are received via a mirror port or an inlinecapture point, the data packets may be analyzed to determine an ingressport by which they were received, or an ingress port identity (step420). Once an ingress port identity associated with the data packet isdetermined, a port stamp identifying the ingress port identity may beinserted into the data packet (step 425). In some embodiments a portstamp may be an 8 bit user-configurable value. In a case where a datapacket includes an FCS and/or a CRC the port stamp may be insertedimmediately preceding the FCS and/or CRC.

In step 430, a new FCS and/or CRC may be calculated in order to reflectthe insertion of a port stamp into the data packet. In step 435, the newFCS and/or CRC may be inserted into the data packet. In step 440, anegress port, like egress port 220, assigned to the data packet may bedetermined. This determination may be based on, for example,configuration information resident in, for example, a device receivingthe traffic flow of data packets. In some cases an egress port assignedto a data packet may be a monitor port. In step 445, the data packetwith the port stamp may be transmitted by, for example, a networkcaptured distribution device like network captured traffic distributiondevice 130 or an ASIC like ASIC 235 to its assigned egress port foreventual transmission to an external device, like external device 150(step 450).

FIG. 5 is a flow chart illustrating a process 500 for inserting a timestamp, like time stamp 335 into a data packet such as data packet 140,301, and/or 305. Process 500 may be performed by, for example, a networkcommunication system like network communication system 100, a networkcaptured traffic distribution device like network captured trafficdistribution device 130, and/or an FPGA like FPGA 240. A data packetgenerated and/or modified by an execution of process 500 may resemble,for example, data packet 145 and/or 303.

In step 505, a traffic flow of captured data packets may be received by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.The traffic flow of data packets may be received via, for example, amirror port like mirror port 160 and/or a traffic capture point locatedalong a communication link between two communicating devices like inlinetraffic capture point 165. The traffic flow of data packets may bereceived at a rate of, for example, ten Mega bites per second, onehundred Mega bites per second, one Gigabit per second, ten Gigabits persecond, 40 Gigabits per second, 40 Gigabits per second via densewavelength-division multiplexing, and 100 Gigabits per second.

In step 510, it may be determined whether a data packet is received viaan inline capture point or a mirror port. When a data packet is receivedvia an inline capture point, the data packet may be echoed to an inlinepair-port resident on, for example, a network captured trafficdistribution device like network captured traffic distribution device130 (step 515). In some embodiments, an inline pair-port may be anegress port resident in, for example, the network captured trafficdistribution device.

When the data packet is received via a mirror port or an inline capturepoint, it may be analyzed to determine a time of arrival of the datapacket (step 520). A time of arrival for a data packet may be indicativeof, for example, a time that the data packet arrived at a networkcaptured traffic distribution device and/or a data packet's position ina sequential traffic flow of data packets.

In step 525, a time stamp value may be generated. The generated timestamp value may be based on, for example, a time value transmitted by asystem clock in communication with, for example, the system, the networkcaptured traffic distribution device, and/or the FPGA, a port timerassociated with the ingress port via which the data packet was received,a difference between the current time of arrival of the data packet andan arrival time of a previously received data packet, and a time valuereceived from a GPS receiver like GPS receiver 170. Generating a timestamp value may also include receiving a value from a first and/orsecond counter such as first counter 245 and/or second counter 250 and,in some cases, combining these values together to generate a time stampvalue. Generating the time stamp value may also include adjusting thevalue of the time stamp based on, for example, a perceived accuracy ofthe determination of the time stamp value. In step 530, the time stampmay be inserted into the data packets. In cases where the data packetincludes an FCS and/or CRC the time stamp may be inserted immediatelypreceding the FCS and/or CRC.

In step 535, a new FCS and/or CRC may be calculated in order to reflectthe insertion of a time stamp into the data packet. In step 540, the newFCS and/or CRC may be incorporated into the data packet. In step 545, anegress port, like egress port 220, assigned to the data packet may bedetermined. This determination may be based on, for example,configuration information resident in, for example, a device receivingthe traffic flow of data packets. In some cases an egress port assignedto a data packet may be a monitor port. In step 550, the data packetwith the time stamp may be transmitted by, for example, a networkcaptured distribution device like network captured traffic distributiondevice 130 or an ASIC like ASIC 235 to its assigned egress port foreventual transmission to an external device like external device 150(step 555). Following step 555, process 500 may end.

FIG. 6 is a flow chart illustrating a process 600 for inserting a timestamp, like time stamp 335, and/or a port stamp, like port stamp 330,into a data packet, such as data packet 140, 301, 302, and/or 305.Process 600 may be performed by, for example, a network communicationsystem like network communication system 100, a network captured trafficdistribution device like network captured traffic distribution device130, and/or an FPGA like FPGA 240. A data packet generated and/ormodified by an execution of process 600 may resemble, for example, datapacket 145 and/or 304.

In step 605, a traffic flow of captured data packets may be received by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.The traffic flow of data packets may be received via, for example, amirror port like mirror port 160 and/or a traffic capture point locatedalong a communication link between two communicating devices liketraffic capture point 165. The traffic flow of data packets may bereceived at a rate of, for example, ten Mega bites per second, onehundred Mega bites per second, one Gigabit per second, ten Gigabits persecond, 40 Gigabits per second, 40 Gigabits per second via densewavelength-division multiplexing, and 100 Gigabits per second.

In step 610, it is determined whether a time stamp is to be insertedinto a data packet. The determination of step 610 may be made accordingto, for example, configuration information resident in the networkcaptured traffic distribution device, and/or an analysis of a datapacket according to a criterion such as a data packet's source,destination, or ingress port. If a time stamp is to be inserted, then atime of arrival of the data packet at the network captured trafficdistribution device may be determined (step 615). Step 615 may resemblestep 520. At step 620, a time stamp may be generated. Step 620 mayresemble step 525. At step 625, a time stamp may be inserted into thedata packet. Step 625 may resemble step 530.

When a time stamp is not to be inserted into a data packet and/orexecution of step 625 is complete, it may be determined whether a portstamp is to be inserted into the data packet (step 630). Thedetermination of step 630 may be made according to, for example,configuration information resident in the network captured trafficdistribution device and/or an analysis of a data packet according to acriterion such as a data packet's source, destination, or ingress port.If a port stamp is not to be inserted into the data packet, process 600may end. When a port stamp is to be inserted into the data packet, thenan ingress port identity for the data packet may be determined. Step 635may resemble step 420. In step 640, a port stamp identifying an ingressport identity may be inserted into the data packet. While the port stampand/or time stamp may be inserted into any location of a data packet, inone embodiment wherein the data packet includes a FCS and/or CRC, theport stamp may be inserted immediately preceding the FCS and/or CRC andthe time stamp may be inserted immediately preceding the port stamp.Following step 640, process 600 may end.

FIG. 7 is a flow chart illustrating a process 700 for deleting apredefined segment from a data packet. Process 700 may be performed by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.A data packet generated and/or modified by an execution of process 700may resemble, for example, data packet 145 and/or 306.

In step 705, a traffic flow of captured data packets may be received by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.The traffic flow of data packets may be received via, for example, amirror port like mirror port 160 and/or a traffic capture point locatedalong a communication link between two communicating devices like inlinetraffic capture point 165. The traffic flow of data packets may bereceived at a rate of, for example, ten Mega bites per second, onehundred Mega bites per second, one Gigabit per second, ten Gigabits persecond, 40 Gigabits per second, 40 Gigabits per second via densewavelength-division multiplexing, and 100 Gigabits per second.

In step 710, it may be determined whether a data packet is received viaan inline capture point or a mirror port. When a data packet is receivedvia an inline capture point the data packet may be echoed to an inlinepair-port resident on, for example, a network captured trafficdistribution device like network captured traffic distribution device130 (step 715). In some embodiments, an inline pair-port may be anegress port resident in, for example, the network captured trafficdistribution device.

When received from a mirror port or an inline capture, at step 720, thedata packet may be analyzed to locate a predefined segment of data to bedeleted from the data packet. Exemplary predefined segments to bedeleted from a data packet include a VLAN tag, GTP information, and MPLSinformation. The analysis of step 720 may be performed by, for example,FPGA 240, ASIC 235, and/or processor 215 and may include, for example,counting in a pre-defined number of bits into a data packet and/oranalyzing the data packet to locate the particular category or type ofdata within the data packet.

On some occasions, the analysis of step 720 may be performed inaccordance with one or more contract terms, privacy policies,communication protocols, and/or laws, such as wire-tapping laws andexemplary predefined segments may include data that is deemed sensitive,or private, under one or more of the privacy policies, protocols, and/orlaws. Exemplary sensitive data includes private conversations betweentwo or more individuals, data categorized as “classified” or “topsecret” by a governmental organization, data characterized as sensitiveunder a contract, like a non-disclosure agreement (NDA), and dataclassified as a trade secret by a business organization. Transmission ofsuch sensitive information to an external device may violate, forexample, one or more applicable contracts, privacy policies,communication protocols, and/or laws.

Once the predefined segment of data to be deleted is located, it may bedeleted from the data packet (step 725). Deletion of the predefinedsegment may bring transmission of the data packet to an external deviceinto compliance with, for example, one or more applicable contracts,privacy policies, communication protocols, and/or laws.

In step 730, a new FCS and/or CRC may be calculated in order to reflectthe deletion of a predefined segment from the data packet. In step 735,the new FCS and/or CRC may be incorporated into the data packet. In step740, an egress port, like egress port 220, assigned to the data packetmay be determined. This determination may be based on, for example,configuration information resident in, for example, a device receivingthe traffic flow of data packets. In some cases an egress port assignedto a data packet may be a monitor port. In step 745, the data packetwithout the deleted predefined segment may be transmitted by, forexample, a network captured distribution device like network capturedtraffic distribution device 130 or an ASIC like ASIC 235 to its assignedegress port for eventual transmission to an external device likeexternal device 150 (step 750). Following step 750, process 700 may end.

FIG. 8 is a flow chart illustrating a process 800 for truncating a datapacket. Process 800 may be performed by, for example, a networkcommunication system like network communication system 100, a networkcaptured traffic distribution device like network captured trafficdistribution device 130, and/or an FPGA like FPGA 240. A data packetgenerated and/or modified by an execution of process 800 may resemble,for example, data packet 145 and/or 307.

In step 805, a traffic flow of captured data packets may be received by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.The traffic flow of data packets may be received via, for example, amirror port like mirror port 160 and/or a traffic capture point locatedalong a communication link between two communicating devices like inlinetraffic capture point 165. The traffic flow of data packets may bereceived at a rate of, for example, ten Mega bites per second, onehundred Mega bites per second, one Gigabit per second, ten Gigabits persecond, 40 Gigabits per second, 40 Gigabits per second via densewavelength-division multiplexing, and 100 Gigabits per second.

In step 810, it may be determined whether a data packet is received viaan inline capture point or a mirror port. When a data packet is receivedvia an inline capture point the data packet may be echoed to an inlinepair-port resident on, for example, a network captured trafficdistribution device like network captured traffic distribution device130 (step 815). In some embodiments, an inline pair-port may be anegress port resident in, for example, the network captured trafficdistribution device.

When received from a mirror port or an inline capture, at step 820, thereceived data packet resembling, for example, data packet 305, may beanalyzed to locate a predefined segment that may resemble, for example,predefined segment 340. Exemplary predefined segments may include headerinformation such as header 315, a VLAN tag, GTP information, and MPLSinformation and/or certain types or categories of information. Theanalysis of step 820 may be performed by, for example, FPGA 240, ASIC235, and/or processor 215 and may include, for example, counting in apre-defined number of bits into a data packet and/or analyzing the datapacket to locate the particular category or type of data within the datapacket.

On some occasions, the analysis of step 820 may be performed inaccordance with one or more contract terms, privacy policies,communication protocols, and/or laws, such as wire-tapping laws andexemplary predefined segments may include data that is not deemedsensitive, or private, under one or more of the privacy policies,protocols, and/or laws. Exemplary sensitive data includes privateconversations between two or more individuals, data categorized as“classified” or “top secret” by a governmental organization, datacharacterized as sensitive under a contract, like a non-disclosureagreement (NDA), and data classified as a trade secret by a businessorganization. Transmission of such sensitive information to an externaldevice may violate, for example, one or more applicable contracts,privacy policies, communication protocols, and/or laws.

Once the predefined segment is located, the data packet may be truncatedto include, for example, only the predefined segment, header, and/orFCS/CRC (step 825). Truncating the data packet to include only thepredefined segment, header, and/or FCS/CRC may bring transmission of thedata packet to an external device into compliance with, for example, oneor more applicable contracts, privacy policies, communication protocols,and/or laws.

In step 830, a new FCS and/or CRC may be calculated in order to reflectthe truncation of the data packet. In step 835 the new FCS and/or CRCmay be incorporated into the data packet. In step 840, an egress port,like egress port 220, assigned to the data packet may be determined.This determination may be based on, for example, configurationinformation resident in, for example, a device receiving the trafficflow of data packets. In some cases an egress port assigned to a datapacket may be a monitor port. In step 845, the data packet with the portstamp may be transmitted by, for example, a network captureddistribution device like network captured traffic distribution device130 or an ASIC like ASIC 235 to its assigned egress port for eventualtransmission to an external device like external device 150 (step 850).

FIG. 9 is a flow chart illustrating a process 900 for inserting a newdata segment into a data packet. Process 900 may be performed by, forexample, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.A data packet generated and/or modified by an execution of process 900may resemble, for example, data packet 145 and/or 308.

In step 905, a traffic flow of captured data packets may be received by,for example, a network communication system like network communicationsystem 100, a network captured traffic distribution device like networkcaptured traffic distribution device 130, and/or an FPGA like FPGA 240.The traffic flow of data packets may be received via, for example, amirror port like mirror port 160 and/or a traffic capture point locatedalong a communication link between two communicating devices like inlinetraffic capture point 165. The traffic flow of data packets may bereceived at a rate of, for example, ten Mega bites per second, onehundred Mega bites per second, one Gigabit per second, ten Gigabits persecond, 40 Gigabits per second, 40 Gigabits per second via densewavelength-division multiplexing, and 100 Gigabits per second.

In step 910, it may be determined whether a data packet is received viaan inline capture point or a mirror port. When a data packet is receivedvia an inline capture point, the data packet may be echoed to an inlinepair-port resident on, for example, a network captured trafficdistribution device like network captured traffic distribution device130 (step 915). In some embodiments, an inline pair-port may be anegress port resident in, for example, the network captured trafficdistribution device.

When received from a mirror port or an inline capture, at step 920, thereceived data packet resembling data packet 140 and/or 301 may beanalyzed to locate an insertion point for a new data segment. Exemplarynew data segments include a new VLAN tag, MPLS information, sourceinformation, destination information, filtering information, a timestamp, a port stamp, and/or additional tracking information. In somecases, the new information will be pre-generated. Once an insertionpoint is located, a new data segment, like new data segment 345, may beinserted at the insertion point (step 925).

In step 930, a new FCS and/or CRC may be calculated in order to reflectthe insertion of a new data segment into the data packet. In step 935,the new FCS and/or CRC may be incorporated into the data packet. In step940, an egress port, like egress port 220, assigned to the data packetmay be determined. This determination may be based on, for example,configuration information resident in, for example, a device receivingthe traffic flow of data packets. In some cases an egress port assignedto a data packet may be a monitor port. In step 945, the data packetwith the new data segment may be transmitted by, for example, a networkcaptured distribution device like network captured traffic distributiondevice 130 or an ASIC like ASIC 235 to its assigned egress port foreventual transmission to an external device like external device 150(step 950). Following step 950, process 900 may end.

FIG. 10 is a flow chart illustrating a process 1000 for modifying apredefined segment of data included in a data packet like data packet301, 305, and/or 140. Process 1000 may be performed by, for example, anetwork communication system like network communication system 100, anetwork captured traffic distribution device like network capturedtraffic distribution device 130, and/or an FPGA like FPGA 240. A datapacket generated and/or modified by an execution of process 1000 mayresemble, for example, data packet 145 and/or 309.

In step 1005, a traffic flow of captured data packets may be receivedby, for example, a network communication system like networkcommunication system 100, a network captured traffic distribution devicelike network captured traffic distribution device 130, and/or an FPGAlike FPGA 240. The traffic flow of data packets may be received via, forexample, a mirror port like mirror port 160 and/or a traffic capturepoint located along a communication link between two communicatingdevices like inline traffic capture point 165. The traffic flow of datapackets may be received at a rate of, for example, ten Mega bites persecond, one hundred Mega bites per second, one Gigabit per second, tenGigabits per second, 40 Gigabits per second, 40 Gigabits per second viadense wavelength-division multiplexing, and 100 Gigabits per second.

In step 1010, it may be determined whether a data packet is received viaan inline capture point or a mirror port. When a data packet is receivedvia an inline capture point the data packet may be echoed to an inlinepair-port resident on, for example, a network captured trafficdistribution device like network captured traffic distribution device130 (step 1015). In some embodiments, an inline pair-port may be anegress port resident in, for example, a network captured trafficdistribution device.

When received from a mirror port or an inline capture, at step 1020, thereceived data packet may be analyzed to locate a predefined segment ofdata, like predefined segment 340, and to be modified. Exemplarypredefined segments to be modified header information such as header315, a VLAN tag, GTP information, and MPLS information, and/or any otherdata present in the data packet which a user, such as user/administrator155, may wish to modify. The analysis of step 1020 may be performed by,for example, FPGA 240, ASIC 235, and/or processor 215 and may include,for example, counting in a pre-defined number of bits into a data packetand/or analyzing the data packet to locate the particular category ortype of data within the data packet.

On some occasions, the analysis of step 1020 may be performed inaccordance with one or more contract terms, privacy policies,communication protocols, and/or laws, such as wire-tapping laws andexemplary predefined segments may include data that is deemed sensitive,or private, under one or more of the privacy policies, protocols, and/orlaws. Exemplary sensitive data includes private conversations betweentwo or more individuals, data categorized as “classified” or “topsecret” by a governmental organization, data characterized as sensitiveunder a contract, like a non-disclosure agreement (NDA), and dataclassified as a trade secret by a business organization. Transmission ofsuch sensitive information to an external device may violate, forexample, one or more applicable contracts, privacy policies,communication protocols, and/or laws.

In step 1025, the data included in the predefined segment may bemodified to generate a modified predefined segment such as modifiedpredefined segment 350. Once the predefined segment is located, the datapacket may be modified to include, for example, a modified predefinedsegment such as modified predefined segment 350. In some instances,modification of the predefined segment may bring transmission of thedata packet to an external device into compliance with, for example, oneor more applicable contracts, privacy policies, communication protocols,and/or laws.

In step 1030, a new FCS and/or CRC may be calculated in order to reflectthe modification of a predefined segment. In step 1035, the new FCSand/or CRC may be incorporated into a data packet. In step 1040, anegress port, like egress port 220, assigned to the data packet may bedetermined. This determination may be based on, for example,configuration information resident in, for example, a device receivingthe traffic flow of data packets. In some cases an egress port assignedto a data packet may be a monitor port. In step 1045, the data packetwith the modified predefined segment may be transmitted by, for example,a network captured distribution device like network captured trafficdistribution device 130 or an ASIC like ASIC 235 to its assigned egressport for eventual transmission to an external device like externaldevice 150 (step 1050).

Thus various apparatus, systems, and methods for modifying a data packethave been herein described.

1. A method comprising: receiving, at a network captured trafficdistribution device, a traffic flow of captured data packets wherein thedata packets are received via at least one of a mirror port resident ona source of the captured data packets and a traffic capture pointlocated along a communication link between two communicating devices,further wherein the network traffic distribution device includes aplurality of ingress and egress ports; analyzing, by the networkcaptured traffic distribution device, a received data packet to locate apredefined segment of data included in the received data packet;modifying, by the network captured traffic distribution device, thepredefined segment of data; determining, by the network captureddistribution device, an egress port assigned to the data packetincluding a modified predefined segment; and transmitting, by thenetwork captured distribution device, the data packet including themodified predefined segment to the assigned egress port.
 2. The methodof claim 1, wherein the analysis includes counting a specified number ofbytes into the data packet.
 3. The method of claim 1, wherein themodified predefined segment has an even number of bytes.
 4. The methodof claim 1, wherein determining the egress port assigned to the datapacket including a modified predefined segment is based on configurationinformation stored on the network captured traffic distribution device.5. The method of claim 1, wherein modifying the predefined segment ofdata includes at least one of removing data from the predefined segment,adding data to the predefined segment, and changing data included in thepredefined segment.
 6. The method of claim 1, wherein the analysisincludes analyzing the data packet according to at least one of aprivacy policy, a communication protocol, a term included in a contract,and a law.
 7. The method of claim 6, wherein modification of thepredefined segment brings transmission of the data packet to an externaldevice into compliance with the at least one of the contract, privacypolicy, communication protocol, and law.
 8. The method of claim 1,wherein the predefined segment includes at least one of a virtual localarea network (VLAN) tag, Gateway General Packet Radio Service (GPRS)Tunneling Protocol (GTP) information, multi-protocol label switching(MPLS) information, data characterized as “private” by a privacy policy,data characterized as “sensitive” under a contract, data categorized as“classified” by a governmental organization, and data categorized as a“trade secret” by a business organization.
 9. A method comprising:receiving, at a network captured traffic distribution device, a trafficflow of captured data packets wherein the data packets are received viaat least one of a mirror port resident on a source of the captured datapackets and a traffic capture point located along a communication linkbetween two communicating devices, further wherein the network trafficdistribution device includes a plurality of ingress and egress ports;analyzing, by the network captured traffic distribution device, areceived data packet to locate a predefined segment of data included ina data packet; truncating, by the network captured traffic distributiondevice, the data packet to include only the predefined segment of data;determining, by the network captured distribution device, an egress portassigned to a truncated data packet; and transmitting, by the networkcaptured distribution device, the truncated data packet to the assignedegress port.
 10. The method of claim 9, wherein a component of thepredefined segment is configurable on a per ingress port basis.
 11. Themethod of claim 9, wherein the data packet includes a payload segmentand truncating the data packet removes a portion of the payload segmentfrom the data packet.
 12. The method of claim 9, wherein the analysisincludes analyzing the data packet according to at least one of aprivacy policy, a communication protocol, a term included in a contract,and a law.
 13. The method of claim 12, wherein truncating the datapacket brings transmission of the data packet to an external device intocompliance with the at least one of the contract, privacy policy,communication protocol, and law.
 14. The method of claim 9, wherein thepredefined segment includes at least one of a virtual local area network(VLAN) tag, Gateway General Packet Radio Service (GPRS) TunnelingProtocol (GTP) information, multi-protocol label switching (MPLS)information, data characterized as “private” by a privacy policy, datacharacterized as “sensitive” under a contract, data categorized as“classified” by a governmental organization, and data categorized as a“trade secret” by a business organization.
 15. A method comprising:receiving, at a network captured traffic distribution device, a trafficflow of captured data packets wherein the data packets are received viaat least one of a mirror port resident on a source of the captured datapackets and a traffic capture point located along a communication linkbetween two communicating devices, further wherein the network trafficdistribution device includes a plurality of ingress and egress ports;analyzing, by the network captured traffic distribution device, areceived data packet to locate a predefined segment of data included inthe received data packet; deleting, by the network captured trafficdistribution device, the predefined segment of data from the datapacket; determining, by the network captured distribution device, anegress port assigned to the data packet including a modified predefinedsegment; and transmitting, by the network captured distribution device,the data packet, without the deleted predefined segment, to the assignedegress port.
 16. The method of claim 15, wherein the analysis includesanalyzing the data packet according to at least one of a privacy policy,a communication protocol, a term included in a contract, and a law. 17.The method of claim 16, wherein deletion of the predefined segmentbrings transmission of the data packet to an external device intocompliance with the at least one of the contract, privacy policy,communication protocol, and law.
 18. The method of claim 15, wherein thepredefined segment includes at least one of a virtual local area network(VLAN) tag, Gateway General Packet Radio Service (GPRS) TunnelingProtocol (GTP) information, multi-protocol label switching(MPLS)information, data characterized as “private” by a privacy policy,data characterized as “sensitive” under a contract, data categorized as“classified” by a governmental organization, and data categorized as a“trade secret” by a business organization.
 19. A network capturedtraffic distribution device comprising; a plurality of ingress ports forreceiving a traffic flow of captured data packets; a memory for storinginstructions executable by at least one of an application specificintegrated circuit (ASIC), a processor, and a field programmable gatearray (FPGA) wherein execution of the instructions enables at least oneof modifying a data packet, removing of a target segment from a datapacket, truncating a data packet, inserting a new data segment into adata packet, modifying a target segment of a data packet, determining anegress port of a plurality of egress ports assigned to the data packet,and transmitting a data packet to the assigned egress port; at least oneof the ASIC, the processor, and the FPGA, wherein the at least one ASIC,the processor, and the FPGA are configured to execute one or more of theinstructions stored in the memory; and the plurality of egress ports fortransmitting a data packet externally from the network captured trafficdistribution device.